docs: Add Goose integration guide and improve MCP setup instructions#63
Merged
docs: Add Goose integration guide and improve MCP setup instructions#63
Conversation
- Add dedicated docs/user/goose.md integration guide - Update FAQ with correct Goose setup instructions (was outdated) - Add recommended MCP setup step to installation and quick-start guides - Add Goose docs link to README.md - Bump version to 3.8.0.dev1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/user/goose.mdintegration guide (matching OpenCode pattern)Why
Goose should have equal weight as an integration option. The FAQ had outdated instructions, and there was no dedicated Goose integration doc like we have for OpenCode.
Test plan